Avoid redirect loop in HTTPSRedirect middleware #1058
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In HTTPSRedirect and similar middlewares, determining if redirection is needed using
c.IsTLS()
causes redirect loop when an application is running behind a TLS termination proxy, e.g. AWS ELB.This is because
c.IsTLS()
always returnsfalse
behind a TLS termination proxy even when a client connects with TLS.Instead, I believe, redirection should be determined by
c.Scheme() != "https"
. This works well even behind a TLS termination proxy thanks to aX-Forwarded-Proto
header the proxy sets.